User data transport over control plane in communication system using designated payload container types

ABSTRACT

Described are systems, devices, methods, and computer program products for user data transport over a control plane in a communication system. For example, a method comprises determining a size of user data to be transmitted over a control plane between user equipment and at least one network entity of a communication system. The method also comprises, in response to determining that the size of the user data to be transmitted is below at least a threshold for small data transport, generating a control plane message comprising the user data to be transmitted in a small data container for transport of user data over the control plane. The method further comprises transmitting the generated control plane message between the user equipment and the at least one network entity of the communication system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Non-Provisional patentapplication Ser. No. 16/937,118, filed Jul. 23, 2020, entitled “UserData Transport over Control Plane in Communication System usingDesignated Payload Container Types,” which claims priority to, and thebenefit of, U.S. Provisional Patent Application No. 62/879,875, filedJul. 29, 2019, entitled “User Data Transport Over Control Plane inCommunication System Using Designated Payload Container Types,” theentire contents of each of which are hereby incorporated herein byreference in their entireties for all purposes.

FIELD

The field relates generally to communication systems, and moreparticularly, but not exclusively, to control plane communicationswithin such systems.

BACKGROUND

This section introduces aspects that may be helpful in facilitating abetter understanding of the inventions. Accordingly, the statements ofthis section are to be read in this light and are not to be understoodas admissions about what is in the prior art or what is not in the priorart.

Fourth generation (4G) wireless mobile telecommunications technology,also known as Long Term Evolution (LTE) technology, was designed toprovide high capacity mobile multimedia with high data ratesparticularly for human interaction. Next generation or fifth generation(5G) technology is intended to be used not only for human interaction,but also for machine type communications in so-called Internet of Things(IoT) networks.

While 5G networks are intended to enable massive IoT services (e.g.,very large numbers of limited capacity devices) and mission-critical IoTservices (e.g., requiring high reliability), improvements over legacymobile communication services are supported in the form of enhancedmobile broadband (eMBB) services providing improved wireless Internetaccess for mobile devices.

In an example communication system, user equipment (5G UE in a 5Gnetwork or, more broadly, a UE) such as a mobile terminal (subscriber)communicates over an air interface with a base station or access pointreferred to as a gNB in a 5G network. The access point (e.g., gNB) isillustratively part of an access network of the communication system.For example, in a 5G network, the access network is referred to as a 5GSystem and is described in 5G Technical Specification (TS) 23.501,V16.0.2, entitled “Technical Specification Group Services and SystemAspects; System Architecture for the 5G System,” the disclosure of whichis incorporated by reference herein in its entirety. In general, theaccess point (e.g., gNB) provides access for the UE to a core network(CN), which then provides access for the UE to other UEs and/or a datanetwork such as a packet data network (e.g., Internet).

TS 23.501 goes on to define a 5G Service-Based Architecture (SBA) whichmodels services as network functions (NFs) that communicate with eachother using representational state transfer application programminginterfaces (Restful APIs).

Furthermore, 5G Technical Specification (TS) 33.501, V15.4.0, entitled“Technical Specification Group Services and System Aspects; SecurityArchitecture and Procedures for the 5G System,” the disclosure of whichis incorporated by reference herein in its entirety, further describessecurity management details associated with a 5G network.

Network performance is an important consideration in any communicationsystem. For example, processing of control plane messages received bythe core network from user equipment can have a significant impact onnetwork performance. However, management of such communications presentsseveral challenges in existing 5G approaches.

SUMMARY

Illustrative embodiments provide improved techniques for user datatransport over a control plane in a communication system usingdesignated payload container types.

For example, in one illustrative embodiment, a method comprisesdetermining a size of user data to be transmitted over a control planefrom user equipment to at least one network entity of a communicationsystem. The method also comprises, in response to determining that thesize of the user data to be transmitted is below at least a thresholdfor small data transport, generating a control plane message comprisingthe user data to be transmitted in a payload container dedicated totransport of small user data over the control plane, hereinafterreferred to as small data container. The method further comprisestransmitting the generated control plane message from the user equipmentto the at least one network entity of the communication system.

In another illustrative embodiment, a method comprises determining asize of user data to be transmitted from at least one network entity ofa communication system over a control plane to the user equipment. Themethod also comprises, in response to determining that the size of theuser data to be transmitted is below at least a threshold for small datatransport, generating a control plane message comprising the user datato be transmitted in a small data container. The method furthercomprises transmitting the generated control plane message to the userequipment from the at least one network entity of the communicationsystem.

Further illustrative embodiments are provided in the form of anon-transitory computer-readable storage medium having embodied thereinexecutable program code that when executed by a processor causes theprocessor to perform the above steps. Still further illustrativeembodiments comprise an apparatus with a processor and a memoryconfigured to perform the above steps.

These and other features and advantages of embodiments described hereinwill become more apparent from the accompanying drawings and thefollowing detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a communication system with which one or moreillustrative embodiments are implemented.

FIG. 2 illustrates processing architectures for user equipment and anetwork entity with which one or more illustrative embodiments areimplemented.

FIG. 3 illustrates part of a communication system, with which one ormore illustrative embodiments are implemented, where user equipmenttransfers data via a control plane to a data network.

FIG. 4 illustrates uplink transfer of small data for user equipment inan idle mode, according to an illustrative embodiment.

FIG. 5 illustrates uplink transfer of small data for user equipment in aconnected mode, according to an illustrative embodiment.

FIG. 6 illustrates downlink transfer of small data for user equipment,according to an illustrative embodiment.

FIG. 7 illustrates a structure of a small data container informationelement, according to an illustrative embodiment.

FIG. 8 illustrates the small data container contents, according to anillustrative embodiment.

FIG. 9 illustrates contents of the small data container informationelement, according to an illustrative embodiment.

FIG. 10 illustrates a structure of a user data container informationelement, according to an illustrative embodiment.

FIG. 11 illustrates the user data container contents, according to anillustrative embodiment.

FIG. 12 illustrates contents of the user data container informationelement, according to an illustrative embodiment.

FIG. 13 illustrates message and information element usage for small datacontainers, according to an illustrative embodiment.

FIG. 14 illustrates a structure of a payload container informationelement, according to an illustrative embodiment.

FIG. 15 illustrates a structure of a payload container type informationelement, according to an illustrative embodiment.

FIG. 16 illustrates contents of a payload container information element,according to an illustrative embodiment.

FIG. 17 illustrates a control plane data size configuration, accordingto an illustrative embodiment.

FIG. 18 illustrates data protection for small data containers for userequipment in an idle mode, according to an illustrative embodiment.

FIG. 19 illustrates a control plane-based user data transportmethodology using designated payload container types, according to anillustrative embodiment.

DETAILED DESCRIPTION

Embodiments will be illustrated herein in conjunction with examplecommunication systems and associated techniques for user data transportover a control plane in a communication system using designated payloadcontainer types. It should be understood, however, that the scope of theclaims is not limited to particular types of communication systemsand/or processes disclosed. Embodiments can be implemented in a widevariety of other types of communication systems, using alternativeprocesses and operations. For example, although illustrated in thecontext of wireless cellular systems utilizing 3GPP system elements suchas a 3GPP next generation system (5G), the disclosed embodiments can beadapted in a straightforward manner to a variety of other types ofcommunication systems. Note that 3GPP stands for 3rd GenerationPartnership Project which is a standards organization that developsprotocols for mobile telephony and the like.

In accordance with illustrative embodiments implemented in a 5Gcommunication system environment, one or more 3GPP technicalspecifications (TS) and technical reports (TR) provide furtherexplanation of user equipment and network entities (e.g., networkelements, network functions, etc.) and/or operations that interact withone or more illustrative embodiments, e.g., the above-referenced 3GPP TS23.501 and 3GPP TS 33.501. Other 3GPP TS/TR documents provide otherconventional details that one of ordinary skill in the art will realize.For example, 5G Technical Specification (TS) 23.401, V16.2.0, entitled“Technical Specification Group Services and System Aspects; GeneralPacket Radio Service (GPRS) Enhancements for Evolved UniversalTerrestrial Radio Access Network (E-UTRAN) Access,” the disclosure ofwhich is incorporated by reference herein in its entirety, describesgeneral principles for Cellular IoT (CIoT) optimizations, anoptimization with which one or more illustrative embodiments will bedescribed below. However, while illustrative embodiments are well-suitedfor implementation associated with the above-mentioned 5G-related 3GPPstandards, alternative embodiments are not necessarily intended to belimited to any particular standards.

Furthermore, illustrative embodiments may be explained herein in thecontext of the Open Systems Interconnection model (OSI model) which is amodel that conceptually characterizes communication functions of acommunication system such as, for example, a 5G network. The OSI modelis typically conceptualized as a hierarchical stack with a given layerserving the layer above and being served by the layer below. Typically,the OSI model comprises seven layers with the top layer of the stackbeing the application layer (layer 7) followed by the presentation layer(layer 6), the session layer (layer 5), the transport layer (layer 4),the network layer (layer 3), the data link layer (layer 2), and thephysical layer (layer 1). One of ordinary skill in the art willappreciate the functions and interworkings of the various layers and,thus, further details of each layer are not described herein. However,it is to be appreciated that while illustrative embodiments arewell-suited for implementations that utilize an OSI model, alternativeembodiments are not necessarily limited to any particular communicationfunction model.

Illustrative embodiments are related to control plane message managementassociated with the Service-Based Architecture (SBA) for 5G networks.Prior to describing such illustrative embodiments, a general descriptionof main components of a 5G network will be described below in thecontext of FIGS. 1 and 2.

FIG. 1 shows a communication system 100 within which illustrativeembodiments are implemented. It is to be understood that the elementsshown in communication system 100 are intended to represent mainfunctions provided within the system, e.g., UE access functions,mobility management functions, authentication functions, serving gatewayfunctions, etc. As such, the blocks shown in FIG. 1 reference specificelements in 5G networks that provide these main functions. However,other network elements may be used in other embodiments to implementsome or all of the main functions represented. Also, it is to beunderstood that not all functions of a 5G network are depicted inFIG. 1. Rather, functions that facilitate an explanation of illustrativeembodiments are represented. Subsequent figures may depict someadditional elements/functions.

Accordingly, as shown, communication system 100 comprises user equipment(UE) 102 that communicates via an air interface 103 with an access point(gNB) 104. The UE 102 in some embodiments is a mobile station, and sucha mobile station may comprise, by way of example, a mobile telephone, acomputer, or any other type of communication device. The term “userequipment” as used herein is therefore intended to be construed broadly,so as to encompass a variety of different types of mobile stations,subscriber stations or, more generally, communication devices, includingexamples such as a combination of a data card inserted in a laptop orother equipment such as a smart phone or other cellular device. In oneor more illustrative embodiments, user equipment refers to an IoT deviceand, more particularly, supports CIoT optimization as mentioned aboveand as will be further explained herein. In such embodiments when the UEis an IoT device, non-limiting examples of such devices may includesensors, monitors, actuators, robotic devices and/or other machine-baseddevices. Such communication devices are also intended to encompassdevices commonly referred to as access terminals.

In one embodiment, UE 102 is comprised of a Universal Integrated CircuitCard (UICC) part and a Mobile Equipment (ME) part. The UICC is theuser-dependent part of the UE and contains at least one UniversalSubscriber Identity Module (USIM) and appropriate application software.The USIM securely stores the permanent subscription identifier and itsrelated key, which are used to identify and authenticate subscribers toaccess networks. The ME is the user-independent part of the UE andcontains terminal equipment (TE) functions and various mobiletermination (MT) functions.

Note that, in one example, the permanent subscription identifier is anInternational Mobile Subscriber Identity (IMSI) of a UE. In oneembodiment, the IMSI is a fixed 15-digit length and consists of a3-digit Mobile Country Code (MCC), a 3-digit Mobile Network Code (MNC),and a 9-digit Mobile Station Identification Number (MSIN). In a 5Gcommunication system, an IMSI is referred to as a Subscription PermanentIdentifier (SUPI). In the case of an IMSI as a SUPI, the MSIN providesthe subscriber identity. Thus, only the MSIN portion of the IMSItypically needs to be encrypted. The MNC and MCC portions of the IMSIprovide routing information, used by the serving network to route to thecorrect home network. When the MSIN of a SUPI is encrypted, it isreferred to as a Subscription Concealed Identifier (SUCI).

The access point 104 is illustratively part of an access network of thecommunication system 100. Such an access network comprises, for example,a 5G System having a plurality of base stations and one or moreassociated radio network control functions. The base stations and radionetwork control functions in some embodiments are logically separateentities, but in other embodiments are implemented in the same physicalnetwork element, such as, for example, a base station router or cellularaccess point.

The access point 104 in this illustrative embodiment is operativelycoupled to mobility management functions 106. In a 5G network, themobility management function is implemented by an Access and MobilityManagement Function (AMF). A Security Anchor Function (SEAF) in someembodiments is also implemented with the AMF connecting a UE with themobility management function. A mobility management function, as usedherein, is the element or function (i.e., entity) in the core network(CN) part of the communication system that manages or otherwiseparticipates in, among other network operations, access and mobility(including authentication/authorization) operations with the UE (throughthe access point 104). The AMF may also be referred to herein, moregenerally, as an access and mobility management entity.

While illustrative embodiments will be described below from theperspective of control plane communications between the UE and the AMFin a 5G system environment, it is to be understood that control planemessage management techniques described herein can be applied in astraightforward manner to communication systems other than 5G systems,by way of example only, LTE or other 3GPP systems, as well as anyappropriate non 3GPP systems. By way of example only, in an alternativeembodiment, where the communication system is an LTE system, themobility management function is performed by a Mobility ManagementEntity (MME).

Returning to FIG. 1, AMF 106 in this illustrative embodiment isoperatively coupled to home subscriber functions 108, i.e., one or morefunctions that are resident in the home network of the subscriber. Asshown, some of these functions include the Unified Data Management (UDM)function, as well as an Authentication Server Function (AUSF). The AUSFand UDM (separately or collectively) are also referred to herein, moregenerally, as an authentication entity. In addition, home subscriberfunctions include, but are not limited to, Network Slice SelectionFunction (NSSF), Network Exposure Function (NEF), Network RepositoryFunction (NRF), and Policy Control Function (PCF).

Note that a UE, such as UE 102, is typically subscribed to what isreferred to as a Home Public Land Mobile Network (HPLMN) in which someor all of the home subscriber functions 108 reside. If the UE is roaming(not in the HPLMN), it is typically connected with a Visited Public LandMobile Network (VPLMN) also referred to as a visited or serving network.Some or all of the mobility management functions 106 may reside in theVPLMN, in which case, functions in the VPLMN communicate with functionsin the HPLMN as needed. However, in a non-roaming scenario, mobilitymanagement functions 106 and home subscriber functions 108 can reside inthe same communication network.

The access point 104 is also operatively coupled to a serving gatewayfunction, i.e., Session Management Function (SMF) 110, which isoperatively coupled to a User Plane Function (UPF) 112. UPF 112 isoperatively coupled to a Packet Data Network, e.g., Internet 114. As isknown in 5G and other communication networks, the user plane (UP) ordata plane typically carries network user traffic (user data) while thecontrol plane (CP) typically carries control signaling traffic (controldata). SMF 110 supports functionalities relating to UP subscribersessions, e.g., establishment, modification and release of PDU sessions.UPF 112 supports functionalities to facilitate UP operations, e.g.,packet routing and forwarding, interconnection to the data network(e.g., 114 in FIG. 1), policy enforcement, and data buffering.

It is to be appreciated that FIG. 1 is a simplified illustration in thatnot all communication links and connections between network functions(NFs) and other system elements are illustrated in FIG. 1. Oneordinarily skilled in the art given the various 3GPP TSs/TRs willappreciate the various links and connections not expressly shown or thatmay otherwise be generalized in FIG. 1.

Further typical operations and functions of certain network elements arenot described herein in detail when they are not the focus ofillustrative embodiments but can be found in appropriate 3GPP 5Gdocumentation. It is to be appreciated that the particular arrangementof system elements in FIG. 1 is an example only, and other types andarrangements of additional or alternative elements can be used toimplement a communication system in other embodiments. For example, inother embodiments, the system 100 comprises other elements/functions notexpressly shown herein. Also, although only single elements/functionsare shown in the FIG. 1 embodiment, this is for simplicity and clarityof illustration only. A given alternative embodiment may include largernumbers of such system elements, as well as additional or alternativeelements of a type commonly associated with conventional systemimplementations.

It is also to be noted that while FIG. 1 illustrates system elements assingular functional blocks, the various subnetworks that make up the 5Gnetwork are partitioned into so-called network slices. Network slices(network partitions) comprise a series of network function (NF) sets(i.e., function chains) for each corresponding service type usingnetwork function virtualization (NFV) on a common physicalinfrastructure. The network slices are instantiated as needed for agiven service, e.g., eMBB service, massive IoT service, andmission-critical IoT service. A network slice or function is thusinstantiated when an instance of that network slice or function iscreated. In some embodiments, this involves installing or otherwiserunning the network slice or function on one or more host devices of theunderlying physical infrastructure. UE 102 is configured to access oneor more of these services via gNB 104. NFs can also access services ofother NFs.

Illustrative embodiments provide improved techniques for user datatransport over a control plane of a communication system, particularlyinvolving CIoT optimizations. FIG. 2 is a block diagram of processingarchitectures 200 of two participants, i.e., user equipment and anetwork function/element (e.g., AMF), in a control plane-based user datatransport methodology in an illustrative embodiment. It is to beappreciated that more than two participants may be involved in a controlplane-based user data transport methodology according to illustrativeembodiments. As such, FIG. 2 illustrates processing architecturesassociated with any two of the participants that directly and/orindirectly communicate. Therefore, in illustrative embodiments, eachparticipant in a control plane-based user data transport methodology isunderstood to be configured with the processing architecture shown inFIG. 2.

As shown, user equipment 202 comprises a processor 212 coupled to amemory 216 and interface circuitry 210. The processor 212 of the userequipment 202 includes a control plane data transport processing module214 that may be implemented at least in part in the form of softwareexecuted by the processor. The processing module 214 performscontrol-plane-based user data transport, as well as other operations,described in conjunction with subsequent figures and otherwise herein.The memory 216 of the user equipment 202 includes a control plane datatransport storage module 218 that stores data generated or otherwiseused during control plane-based user data transport and otheroperations.

As further shown, a network function/element 204 comprises a processor222 coupled to a memory 226 and interface circuitry 220. The processor222 of the network function/element 204 includes a control plane datatransport processing module 224 that may be implemented at least in partin the form of software executed by the processor 222. The processingmodule 224 performs control-plane based user data transport, as well asother operations, described in conjunction with subsequent figures andotherwise herein. The memory 226 of the network function/element 204includes a control plane data transport storage module 228 that storesdata generated or otherwise used during control-plane based user datatransport and other operations.

The processors 212 and 222 of the respective user equipment 202 andnetwork function/element 204 may comprise, for example, microprocessors,application-specific integrated circuits (ASICs), field programmablegate arrays (FPGAs), digital signal processors (DSPs) or other types ofprocessing devices or integrated circuits, as well as portions orcombinations of such elements. Such integrated circuit devices, as wellas portions or combinations thereof, are examples of “circuitry” as thatterm is used herein. A wide variety of other arrangements of hardwareand associated software or firmware may be used in implementing theillustrative embodiments.

The memories 216 and 226 of the respective user equipment 202 andnetwork function/element 204 may be used to store one or more softwareprograms that are executed by the respective processors 212 and 222 toimplement at least a portion of the functionality described herein. Forexample, control-plane based user data transport operations and otherfunctionality as described in conjunction with subsequent figures andotherwise herein may be implemented in a straightforward manner usingsoftware code executed by processors 212 and 222.

A given one of the memories 216 or 226 may therefore be viewed as anexample of what is more generally referred to herein as a computerprogram product or still more generally as a processor-readable storagemedium that has executable program code embodied therein. Other examplesof processor-readable storage media may include disks or other types ofmagnetic or optical media, in any combination. Illustrative embodimentscan include articles of manufacture comprising such computer programproducts or other processor-readable storage media.

The memory 216 or 226 may more particularly comprise, for example, anelectronic random-access memory (RAM) such as static RAM (SRAM), dynamicRAM (DRAM) or other types of volatile or non-volatile electronic memory.The latter may include, for example, non-volatile memories such as flashmemory, magnetic RAM (MRAM), phase-change RAM (PC-RAM) or ferroelectricRAM (FRAM). The term “memory” as used herein is intended to be broadlyconstrued, and may additionally or alternatively encompass, for example,a read-only memory (ROM), a disk-based memory, or other type of storagedevice, as well as portions or combinations of such devices.

The interface circuitries 210 and 220 of the respective user equipment202 and network function/element 204 illustratively comprisetransceivers or other communication hardware or firmware that allows theassociated system elements to communicate with one another in the mannerdescribed herein.

It is apparent from FIG. 2 that user equipment 202 is configured forcommunication with network function/element 204 and vice-versa via theirrespective interface circuitries 210 and 220. This communicationinvolves user equipment 202 sending data to network function/element204, and network function/element 204 sending data to user equipment202. However, in alternative embodiments, other network elements orother components may be operatively coupled between, as well as to, userequipment 202 and/or network function/element 204. The term “data” asused herein is intended to be construed broadly, so as to encompass anytype of information that may be sent between control plane messagemanagement participants including, but not limited to, messages, tokens,identifiers, keys, indicators, user data, control data, etc.

It is to be appreciated that the particular arrangement of componentsshown in FIG. 2 is an example only, and numerous alternativeconfigurations are used in other embodiments. For example, any givennetwork element/function can be configured to incorporate additional oralternative components and to support other communication protocols.

Given the above illustrative architectures, illustrative embodiments ofcontrol plane-based user data transport methodologies will be furtherdescribed below in the context of IoT connectivity in 3GPP networks.

3GPP has defined a set of technologies for enabling IoT connectivity in3G and 4G deployments, including via Extended Coverage Global System forMobile Communications (GSM) IoT (EC-GSM-IoT), Narrowband IoT (NB-IoT),and enhanced Machine Type Communication (eMTC). NB-IoT and eMTC radiotechnologies will be used for 5G CIoT deployment.

As mentioned above, general principles of CIoT optimizations aredescribed in the above-referenced TS 23.401 (e.g., clause 4.10:Introduction of C-IoT Evolved Packet System (EPS) Optimizations). Twotypes of communication bearer optimizations are specified. Oneoptimization is based on User Plane (UP) transport of user data and isreferred to as UP CIoT EPS optimization. Another optimization, known asControl Plane (CP) CIoT EPS optimization, transports user data or ShortMessage Service (SMS) messages via the mobility management element (MMEin LTE or AMF in 5G) by encapsulating them in the Non-Access Stratum(NAS), reducing the total number of control plane messages when handlinga short data transaction. NAS is the functional layer in UMTS and LTEwireless telecom protocol stacks between the core network and userequipment. This layer is used to manage the establishment ofcommunication sessions and to maintain continuous communications withthe user equipment as it roams.

When the UE attaches to the network, the UE includes, in a preferrednetwork behavior indication, the network behavior that the UE cansupport and what it would prefer to use, such as whether CP CIoT EPSoptimization is supported or whether UP CIoT EPS optimization issupported.

When CP CIoT EPS optimization is supported, CIoT UEs can send andreceive small data packets over the NAS signalling control plane. Thereare some benefits when the CIoT UEs uses the control plane forcommunication since the control plane is not busy all the time and has arelatively low rate of packets.

A key requirement for IoT devices is battery life. Both Long TermEvolution (LTE) Category M1 (Cat-M1) and NB-IoT are required tosignificantly decrease power consumption over broadband cellulartechnologies. Battery life may be important for various low cost sensorand metering type IoT devices. In NB-IoT, for example, the maximumbattery life is expected to reach 10 years even under extreme coverageconditions. Ideally, the battery for such IoT devices should last forthe entire expected life cycle of the device to avoid costlymaintenance.

In one example embodiment, consider the scenario where a 5G UE 302transfers user data via the control plane (e.g., as illustrated by thedashed line in FIG. 3) to a data network 314 (e.g., a Packet DataNetwork (PDN) such as the Internet) over the N6 interface in a 5Gcommunication system. The UE 302 connects to AMF 308 via 3GPP accesspoint 304 and NG Radio Access Network (NG-RAN) 306 and provides the userdata over the N1 interface. The AMF 308 provides the user data to theSMF 310 over the N11 interface, and the SMF provides the user data tothe UPF 312 over the N4 interface. The UPF 312 provides the data to thedata network 314 over the N6 interface. FIG. 3 also illustratescommunications and interfaces between the AMF 308 and authenticationentity 316, which is assumed to include AUSF 318, UDM 320 and User DataRepository (UDR) 322. The SMF 310 and UDR 322 are also in communicationwith PCF 324 as illustrated.

Data packet size can have significant impacts on IoT device batterylife. For 5G CIoT, there is need for supporting the transfer ofinfrequent “small” data over the control plane. As described in furtherdetail below, a communication system may be configured to define a“small” data size, such as based on the size of typical messages thatare expected to be sent using a particular type of IoT device in 5GCIoT. User-defined thresholds may be used for specifying an appropriatesize range for “small” data as the term is used herein. Whentransporting the small data over the control plane, it is important tominimize the overhead involved in the transport thereby reducing energyconsumption by the IoT device to save battery life.

Illustrative embodiments provide efficient methods for transportinginfrequent small data for IoT devices, advantageously extending batterylife of the IoT devices. In some embodiments, efficient transport of theinfrequent small data is provided over Non-Access Stratum (NAS)signalling. To do so, some embodiments define a dedicated container,referred to herein as a “CIoT small data container” for such small datatransport. The CIoT small data container is treated as a special type ofpayload container type, and the UE 302 and AMF 308 are configured withprocedures for handling the CIoT small data container. In someembodiments, mechanisms are provided to support the configuration of amaximum small data size, along with logic for handling both small datatransport and “large” data transport. In this context, “large” datatransport refers to the transport of data that exceeds user-definedthresholds for “small” data as described above and elsewhere herein.Additional user-defined thresholds may be used to specify a maximum sizefor “large” data transport over the control plane (with larger databeing transported over the user plane).

Techniques are also provided for protection and ciphering of datacontents that are transported over the control plane.

FIG. 4 shows an uplink transfer procedure 400 of small data for UE 302in an idle mode. The UE 302 in the idle mode over 3GPP access may haveuplink user data pending, and the UE may use 5G system (5GS) serviceswith control plane CIoT 5GS optimization. As a prerequisite, it isassumed that the UE 302 is registered 401 with the AMF 308 for CIoTcontrol plane optimizations (CP-CIoT) that a NAS security context 402 isestablished, and that ciphering and integrity protection mechanisms 403are provided. Further, it is assumed that the UE 302 is in the idle mode404 and has uplink user data to send.

In step 405, the UE 302 sets a control plane service type of a controlplane service request message to “mobile originating request.” Inaddition, the UE 302 sets the payload container information element (IE)type to “CIoT small data container.” The UE 302 formats a Protocol DataUnit (PDU) session identifier (ID) and release assistance informationtogether with the data in the CIoT small data container. In someembodiments, the PDU session ID is 4 bits, and the release assistanceinformation is 2 bits. The release assistance information is includedwhen the UE 302 wishes to inform the network of one of two conditions.The first condition is that, subsequent to the current uplink datatransmission, no further uplink and no further downlink datatransmission (e.g., acknowledgments, responses, etc.) is expected. Inother words, the first condition occurs when the upper layers indicatethat data exchanges have completed with the current uplink datatransfer. The second condition is that, subsequent to the current uplinkdata transmission, only a single downlink data transmission and nofurther uplink data transmission is expected. In other words, the secondcondition occurs when the upper layers indicate that data exchanges willhave completed with the next downlink data transmission. It should beappreciated that in other embodiments, different conditions or moregenerally different release assistance information may be utilized. Instep 405, the UE 302 also sets the payload container IE to the CIoTsmall data container.

The UE 302 includes the payload container type and payload containerformatted as described above in a control plane service request messagethat is sent in step 405. If additional information, such as PDUsessions state for PDU session synchronization or CP to UP switchindication (e.g., via uplink data status), such information may beincluded in the step 405 control plane service request message asseparate IEs. The UE 302 then sends the step 405 control plane servicerequest message to the AMF 308 (e.g., via NG-RAN 306). The UE 302 alsostarts a retransmission timer (e.g., T3517) and enters the state“5GMM-SERVICE-REQUEST-INITIATED.”

Upon receipt of the step 405 control plane service request message withthe control plane service type indicating “mobile originating request”,and after completion of the 5GS Mobility Management (5GMM) commonprocedures, the AMF 308 sends a service accept message 409 to the UE302. If the payload container IE is included in the step 405 controlplane service request message, and the payload container type IE is setto “CIoT small data container” and if the payload container IEsuccessfully passes the integrity check, the AMF 308 extracts the PDUsession ID and release assistance information in step 406. The AMF 308forwards the data contents to the SMF 310 in step 407 via anNsmf_PDUSession_DataTransfer request message in step 408. This requestmessage includes the data and PDU session ID.

As noted above, the AMF 308 sends a service accept message 409 to the UE302. The service accept message 409 indicates the PDU session status,and the UE 302 is now in a connected mode 410. At this point, a RadioResource Control (RRC) connection is established 411. If the PDU sessionstatus IE is included in the step 405 control plane service requestmessage, or if the AMF 308 needs to perform a PDU session statussynchronization, the AMF 308 includes a PDU session status IE in theservice accept message 409 to indicate which PDU sessions associatedwith the access type in the service accept message 409 are active in theAMF 308.

The SMF 310 selects a UPF 312 (or a NEF) for user data delivery from theUE 302 based on the configuration in step 412. The SMF 310 thengenerates and sends a PFCP_data forwarding message 413 to the UPF 312.The PFCP_data forwarding message 413 is a Packet Forwarding ControlProtocol (PFCP) message, and includes a tunnel ID, and the payloadcontainer (e.g., user data) from the step 405 control plane servicerequest message.

If the release assistance indication IE is included in the step 405control plane service request message, and if the payload container typeIE is set to “CIoT small data container”, the AMF 308 will act in step414 based on the condition indicated by the release assistanceindication. If the release assistance indication indicates that nofurther uplink or downlink data transmission subsequent to the uplinkdata transmission is expected (e.g., the first condition describedabove), the AMF 308 releases the RRC connection (e.g., the NAS signalingconnection). If the release assistance indication indicates that only asingle downlink data transmission and no further uplink datatransmission subsequent to the uplink data transmission is expected(e.g., the second condition described above), the AMF 308 releases theRRC connection upon subsequent delivery of the next received downlinkdata transmission to the UE 302.

Upon successful completion of the above-described procedure, the UE 302resets a service request attempt counter, stops the timer T3517, andenters a state of “5GMM-REGISTERED.” The UE 302 also treats theindication from the lower layers that the RRC connection has beenreleased as successful completion of the procedure. If the PDU sessionstatus information element is included in the service accept message409, then the UE 302 performs a local release of all those PDU sessionsthat are active on the UE side associated with the 3GPP access but areindicated by the AMF 308 as being inactive.

FIG. 5 shows an uplink transfer procedure 500 of small data for UE 302in a connected mode. The UE 302 in the idle mode over 3GPP access mayhave uplink user data pending, and the UE may use 5GS services withcontrol plane CIoT 5GS optimization. Similar to FIG. 4, it is assumedthat the UE 302 is registered 501 with the AMF 308 for CP-CIoT that aNAS security context 502 is established, and that ciphering andintegrity protection mechanisms 503 are provided. Further, it is assumedthat the UE 302 is in the connected mode 504 and has uplink user data tosend.

In step 505, the UE 302 generates an uplink NAS data transport (UL NASTRANSPORT) message. The UE 302 sets a payload container type IE to “CIoTsmall data container” and formats the PDU session ID and releaseassistance information together with data in the CIoT small datacontainer. Again, the PDU session ID may be 4 bits, while the releaseassistance information is 2 bits. The release assistance information issimilar to that described above in conjunction with FIG. 4, and is usedby the UE 302 to inform the network of the first condition (e.g., thatsubsequent to the current uplink data transmission, no further uplinkand no further downlink data transmission is expected) or the secondcondition (e.g., that subsequent to the current uplink datatransmission, only a single downlink data transmission and no furtheruplink data transmission is expected). It should be appreciated that inother embodiments, different conditions or more generally differentrelease assistance information may be utilized. The UE 302 also sets thepayload container IT to the CIoT small data container.

The UE 302 includes the payload container type and payload container,formatted as described above, in an uplink NAS data transport message instep 505. If additional information such as PDU sessions status for PDUsession synchronization or CP to UP switch indication (e.g., via uplinkdata status) is needed, such information may be included in the step 505uplink NAS data transport message as separate IEs. The UE 302 then sendsthe step 505 uplink NAS data transport message to the AMF 308.

Upon receipt of the step 505 uplink NAS data transport message, if thepayload container IE is included and the payload container type IE isset to “CIoT small data container”, and if the payload container IEsuccessfully passes an integrity check, the AMF 308 extracts the PDUsession ID and release assistance information in step 506. The AMF 308forwards the data to the SMF 310 associated with the UE in step 507,such as via Nsmf_PDUSession_DataTransfer request message 508 similar tothe message 408 described above in conjunction with FIG. 4.

Possible downlink data is provided to the UE 302 in step 509, ifapplicable. The AMF 308 handles the NAS signaling connection release(e.g., RRC release) in step 510 based on the release assistanceinformation that is included in the step 505 uplink NAS data transportmessage. If the release assistance indication indicates that no furtheruplink or downlink data transmission subsequent to the uplink datatransmission is expected (e.g., the first condition described above),the AMF 308 releases the RRC connection (e.g., the NAS signalingconnection). If the release assistance indication indicates that only asingle downlink data transmission and no further uplink datatransmission subsequent to the uplink data transmission is expected(e.g., the second condition described above), the AMF 308 releases theRRC connection upon subsequent delivery of the next received downlinkdata transmission to the UE 302. The RRC connection is released in step511, and the UE 302 enters the idle mode in step 512.

The SMF 310 selects a UPF 312 (or a NEF) for user data delivery from theUE 302 based on the configuration in step 513. The SMF 310 thengenerates and sends a PFCP_data forwarding message 514 to the UPF 312.The PFCP_data forwarding message 514 is similar to that described abovewith respect to the PFCP_data forwarding message 413.

FIGS. 4 and 5 show mobile-originated NAS transport procedures 400 and500 for the UE 302 in the idle and connected modes, respectively. FIG. 6shows a downlink transfer procedure 600 of small data for UE 302 that isnetwork-initiated, providing CIoT user data over the control plane fromthe AMF 308 to the UE 302 in a 5GMM message (e.g., over the N6 interfacein a 5G system). Similar to FIGS. 4 and 5, it is assumed that the UE 302is registered 601 with the AMF 308 for CP-CIoT, that a NAS securitycontext 602 is established, and that ciphering and integrity protectionmechanisms 603 are provided. Further, it is assumed that the UE 302 isin the connected mode 604 and that AMF 308 has downlink user data to besent to the UE 302.

The AMF 308 and SMF 310 have an association established with one anotherin step 605, and the SMF 310 and UPF 312 have a PFCP associationestablished with one another in step 606. The UPF 312 provides aPFCP_data forwarding message to the SMF 310 in step 607. This messageincludes a tunnel ID and a payload container with user data to be sentto the UE 302. The SMF 310 generates and sends aNsmf_PDUSession_DataTransfer Notify message in step 608, including thedata and the PDU session ID.

In step 609, the AMF 308 generates and sends a downlink NAS transportmessage to the UE 302. The AMF 308 sets the payload container type IE to“CIoT small data container” and formats the PDU session ID together withthe downlink data for the UE 302 in the CIoT small data container.Again, the PDU session ID may be formatted as 4 bits. The AMF 308includes the payload container type and the payload container formattedas described above into a downlink NAS data transport message. Ifadditional information, such as PDU session status for PDU sessionsynchronization or CP to UP switch indication (e.g., via uplink datastatus) are needed, such information may be included in the downlink NASdata transport message as separate IEs.

Upon receipt of the downlink NAS data transport message in step 609, ifthe payload container IE is included, if the payload container type IEis set to “CIoT small data container”, and if the payload container IEsuccessfully passes an integrity check, the UE 302 extracts the PDUsession ID and data contents from the payload container IE and forwardsthe data content to the upper layer application.

FIG. 7 shows a structure 700 of a CIoT small data container IE. The CIoTsmall data container IE is used to encapsulate user data transferredbetween the UE 302 and AMF 308. The CIoT small data container IE iscoded as illustrated in FIG. 7. The CIoT small data container, in someembodiments, is a type 4 information element with a minimum length of 3octets and a maximum length of 257 octets. Octet 1 includes the CIoTsmall data container IE identifier (IEI), and octet 2 includes thelength of the CIoT small data container contents. Octets 3 through ninclude the CIoT small data container contents. The value of n is 257,corresponding to a maximum length of the CIoT small data containercontents of 255 (e.g., 257 minus octet 1 used for the CIoT small datacontainer IEI and octet 2 used to indicate the length of the CIoT smalldata container contents). As described in further detail below withrespect to FIG. 8, octet 3 is also reserved in some embodiments, thusthe user data to be transmitted may occupy up to 254 octets.

FIG. 8 shows the CIoT small data container contents (e.g., octets 3through n in the structure 700). Octet 3 includes PDU session identityinformation coded with 4 bits and downlink data expected (DDX) coded in2 bits. Octet 3 also includes two spare bits. Octets 4 through n includethe data contents. FIG. 9 shows contents 900 of the CIoT small datacontainer IE, more particularly illustrating examples of the informationin octets 3 through n. For example, FIG. 9 illustrates how the PDUsession data is coded with 4 bits and how the DDX data is coded with 2bits.

The CIoT small data container is assumed to be “small” in size orlimited to data contents of 255 octets as noted in FIG. 9. A CIoT userdata container may be used to encapsulate “large” user data that istransferred between the UE 302 and AMF 308 up to 65,531 octets. The CIoTuser data container IE is coded as illustrated in FIGS. 10-12.

FIG. 10 shows a structure 1000 of a CIoT user data container IE. TheCIoT user data container, in some embodiments, is a type 6 informationelement with a minimum length of 5 octets and a maximum length of 65,535octets. Octet 1 includes the CIoT user data container IEI, and octets 2and 3 include the length of the CIoT user data container contents.Octets 4 through n include the CIoT user data container contents. 65,531octets are available for the user data to be transmitted, as there arethree overhead octets (e.g., octet 1 including the CIoT user datacontainer IEI and octets 2 and 3 including the length of the CIoT userdata container contents) plus, as described in further detail below,octet 4 is reserved in some embodiments.

FIG. 11 shows the CIoT user data container contents (e.g., octets 4through n in the structure 1000). Octet 4 includes PDU session identityinformation coded with 4 bits and DDX coded in 2 bits. Octet 4 alsoincludes two spare bits. Octets 5 through n include the data contents.FIG. 12 shows contents 1200 of the CIoT user data container IE, moreparticularly illustrating examples of the information in octets 4through n. For example, FIG. 12 illustrates how the PDU session data iscoded with 4 bits and how the DDX data is coded with 2 bits.

When in idle or connected mode, the UE 302 decides whether to send datavia a CIoT user data container or a CIoT small data container based onthe data size to be transported, a configured maximum small data size(e.g., a CP-CIoT_MaxSmallDataSize parameter that is configured as a NASManagement Object (MO) or in a Universal Subscriber Identity Module(USIM) Elementary File (EF)), and a configured maximum data size (e.g.,a CP-CIoT_MaxDataSize configured as a NAS MO or in a USIM EF). When inconnected mode, the AMF 308 decides whether to send the data to the UE302 via the CIoT user data container or the CIoT small data containerbased on the data size to be transported, the configured maximum smalldata size and the configured maximum data size.

More specifically, from the UE 302 side, the decision of whether to usethe CIoT user data container or the CIoT small data container may usethe following algorithm. If the user data size is smaller than theconfigured maximum small data size (e.g., less thanCP-CIoT_MaxSmallDataSize), the UE 302 sends the data using the CIoTsmall data container. If the user data size is larger than theconfigured maximum small data size (e.g., greater thanCP-CIoT_MaxSmallDataSize) and less than 254 octets, the UE 302 sends thedata using the CIoT small data container. If the user data size islarger than 254 octets but less than the configured maximum data size(e.g., less than CP-CIoT_MaxDataSize), the UE 302 sends the data usingthe CIoT user data container. If the user data size is larger than theconfigured maximum data size (e.g., larger than CP-CIoT_MaxDataSize),the UE 302 switches from CP-CIoT optimizations to UP-CIoT optimizations,and sends data using the user plane rather than from the control planevia NAS signaling.

From the network side (e.g., from the AMF 308), the decision of whetherto use the CIoT user data container or the CIoT small data container mayuse the following algorithm. If the user data size is smaller than theconfigured maximum small data size (e.g., less thanCP-CIoT_MaxSmallDataSize), the AMF 308 sends the data using the CIoTsmall data container. If the user data size is larger than theconfigured maximum small data size (e.g., greater thanCP-CIoT_MaxSmallDataSize) and less than 254 octets, the AMF 308 sendsthe data using the CIoT small data container. If the user data size islarger than 254 octets but less than the configured maximum data size(e.g., less than CP-CIoT_MaxDataSize), the AMF 308 sends the data usingthe CIoT user data container. If the user data size is larger than theconfigured maximum data size (e.g., larger than CP-CIoT_MaxDataSize),the AMF 308 switches from CP-CIoT optimizations to UP-CIoT optimizationsand sends the data using the user plane rather than using the controlplane via NAS signaling.

FIG. 13 shows message and IE usage for CIoT small data containers andCIoT user data containers. Tables 1301, 1302 and 1303 illustrate messagecontent for uplink NAS transport messages (e.g., as used in step 505 inFIG. 5), downlink NAS transport messages (e.g., as used in step 609 inFIG. 6) and control plane service request messages (e.g., as used instep 405 in FIG. 4), respectively. The payload container of each of thetables 1301, 1302 and 1303 is one of the payload container typesillustrated in table 1304 (e.g., one of the CIoT small data containerand the CIoT user data container). Tables 1305 and 1306 illustrate thestructures of these payload container types. More particular, table 1305illustrates the structure of the CIoT small data container and table1306 illustrates the structure of the CIoT user data container.

The payload container IE is used to transport one or more payloads. Ifmultiple payloads are transported, the associated information of eachpayload is also transported together with the payload. The payloadcontainer IE is coded as shown in FIG. 14. The payload container IE 1400of FIG. 14, in some embodiments, is a type 6 information element with aminimum length of 4 octets and a maximum length of 65,538 octets. Thepayload container contents (octet 4 to octet n) have a maximum value of65,535 octets.

If the payload container type is set to “CIoT small data container” andis included in the control plane service request message (e.g., as usedin step 405 in FIG. 4), the payload container contents are coded thesame way as the contents of the CIoT small data container IE except thatthe first two octets are not included.

If the payload container type is set to “CIoT small data container” andis included in an uplink NS transport message (e.g., as used in step 505of FIG. 5), the payload container contents are coded the same way as thecontents of the CIoT small data container IE except that the first twooctets are not included.

If the payload container type is set to “CIoT small data container” andis included in the downlink NS transport message (e.g., as used in step609 in FIG. 6), the payload container contents are coded the same way asthe contents of the CIoT small data container IE except that the firsttwo octets are not included.

If the payload container type is set to “CIoT user data container” andis included in the uplink NAS transport message (e.g., as used in step505 in FIG. 5), the payload container contents are coded the same way asthe contents of the CIoT user data container IE except that the firstthree octets are not included.

If the payload container type is set to “CIoT user data container” andis included in the downlink NAS transport message (e.g., as used in step609 in FIG. 6), the payload container contents are coded the same way asthe contents of the CIoT user data container IE except that the firstthree octets are not included.

If the payload container type is set to “CIoT user data container” andis included in the control plane service request message (e.g., as usedin step 405 in FIG. 4), the payload container contents are coded thesame way as the contents of the CIoT user data container IE except thatthe first three octets are not included.

In some embodiments, new payload container types are defined for “CIoTsmall data container” and “CIoT user data container.” The purpose of thepayload container type IE is to indicate that type of payload includedin the payload container IE. FIG. 15 shows a structure 1500 of a payloadcontainer type IE, with bits 1-4 in octet 1 used to provide the payloadcontainer type value and bites 5-8 in octet 1 used to provide thepayload container type IE. FIG. 16 shows coding 1600 of the payloadcontainer type value in bits 1-4 of octet 1 of the payload containertype IE 1500. As illustrate, a short message service (SMS) message maybe coded in bits 4 3 2 1 and 0 0 1 0, the CIoT user data container maybe coded in bits 4 3 2 1 and 1 0 0 0, and the CIoT small data containermay be coded in bits 4 3 2 1 as 1 0 0 1.

FIG. 17 shows a control plane data size configuration 1700. Moreparticularly, the control plane data size configuration 1700 is providein a NAS MO, with a maximum data size parameter (e.g.,CP-CIoT_MaxDataSize) and a maximum small data size parameter (e.g.,CP-CIoT_MaxSmallDataSize).

The CP-CIoTMaxDataSize leaf of the NAS MO indicates a configured maximumuser data size that can be transported over the control plane via NASsignaling when in a Home Public Land Mobile Network (HPLMN) orEquivalent HPLMN (EHPLMN), as described in 3GPP TS 23.122. Theoccurrence of this leaf is zero or one, with a format of int (integer),access types of “Get” and “Replace” and a value in the range of 0 to 65,531. If not provisioned, a default value of 65,531 octets is used forthis leaf.

The CP-CIoT_MaxSmallDataSize leaf of the NAS MO indicates a configuredmaximum small data size that can be transported over the control planevia NAS signaling when in the HPLMN or EHPLMN. The occurrence of thisleaf is zero or one, with a format of int, access types of “Get” and“Replace” and a value in the range of 0 to 254. If not provisioned, adefault value of 254 is used for this leaf.

The configuration parameters (e.g., in the NAS MO shown in FIG. 17) maybe set by a device's Home Network Operator (HNO), based on devicecategory and pattern (e.g., including typical data size and sendingfrequency), and device physical layer transport block size. eMTC Cat-M1type devices have a downlink (DL) Transport Block Size (TBS) of 1000bits (e.g., 125 octets) and an uplink (UL) TBS of 1000 bits (in 3GPPRelease 13) and 2984 in 3GPP Release 14. eMTC Cat-M2 type devices have aDL TBS of 4008 bits and an UL TBS of 2984 for 1.4 Megahertz (MHz) and6968 for 5 MHz. NB-IoT Cat-NB1 type devices have a DL TBS of 860 bits(e.g., about 110 octets) and an UL TBS of 1000 bits (e.g., about 125octets). NB-IoT Cat-NB2 type devices have a DL TBS of 2536 bits and ULTBS of 2536 bits. The CIoT small data container is thus sufficient forNB-IoT Cat-NB1 type devices, and is also suitable for eMTC Cat-M1 typedevices. For other types of devices, the CIoT user data container may bedesired as it can support transport of data up to 65,531 octets.

The protection of small data sent in the step 405 control plane servicerequest message when the UE 302 is in idle mode (e.g., as in FIG. 4) maybe achieved as described below. When the UE 302 is in a connected mode(e.g., as in FIGS. 5 and 6), a secure NAS connection is alreadyestablished and no additional protection of small data is needed.

To reduce overall message overhead, instead of ciphering the entiremessage only the non-cleartext IEs are ciphered in some embodiments.After the UE 302 formats the payload container, the UE 302 includes thepayload container type IE, payload container IE and other non-cleartextIEs in the NAS message container IE and ciphers the value part of theNAS message container IE using the ciphering key from the NAS securitycontext of the UE 302. This is illustrated in the example control planeservice request message content 1800 shown in FIG. 18. The UE 302 setsthe security header type of the step 405 control plane service requestmessage to “integrity protected” and sends the control plane servicerequest message containing the cleartext IEs and the NAS messagecontainer IE to the network (e.g., to AMF 308).

When the AMF 308 receives an integrity protected control plane servicerequest message that includes a NAS message container IE, the AMF 308performs the integrity check at the network side. Once the integritycheck is successful, the AMF 308 deciphers the value part of the NASmessage container IE and extracts the payload container type IE, payloadcontainer IE and other non-cleartext IEs.

If a control plane service request message fails the integrity check atthe network side and the UE 302 has only non-emergency PDU sessionsestablished, the AMF 308 sends a service reject message with 5GMM cause#9 (“UE identity cannot be derived by the network”) and keeps the5GMM-content and 5G NAS security context unchanged.

As illustrated in FIG. 18, the cleartext IEs of the control planeservice request message include: extended protocol discriminator;security header type; spare half octet; ngKSI (ng Key Set Identifier);control plane service request message identity; and control planeservice type. The rest of the IEs shown in FIG. 18 are non-cleartextIEs, including: payload container type; payload container IE; PDUsession ID; PDU session status; uplink status; release assistanceinformation IE; etc.

If the data to be transported exceeds the CIoT_MaxSmallDataSizeparameter, the larger CIoT user data container is used to buffer userdata. The handling logic of transporting large IoT data for the UE 302in both the idle mode and the connected mode is the same as describedabove, except that the payload container type IE is set to “CIoT userdata container” and the payload container IE is set to the value part ofthe CIoT user data container. The logic for ciphering large IoT data forthe UE 302 in the idle mode (e.g., as in FIG. 4) may be the same as thatdescribed above for small IoT data.

FIG. 19 illustrates a control plane-based user data transportmethodology 1900, according to an illustrative embodiment. As shown, instep 1902, the method comprises determining a size of user data to betransmitted between user equipment (e.g., UE 302) and a data network(e.g., data network 314). Responsive to determining that the size of theuser data to be transmitted is below at least a threshold for small datatransport, a control plane message is generated in step 1904. Thegenerated control plane message comprises the user data to betransmitted and specifies a designated payload container type reservedfor transport of user data over a control plane between the userequipment and at least one network entity (e.g., AMF 308) of acommunication system coupling the user equipment to the data network. Instep 1906, the generated control plane message is transmitted betweenthe user equipment and the at least one network entity of thecommunication system.

The methodology 1900 may be performed by the user equipment, which maybe part of an IoT device.

If the user equipment is in an idle mode, the generated control planemessage may comprise a control plane service request message with acontrol plane service type set to indicate a user equipment-originatingrequest, and step 1906 may comprise transmitting the generated controlplane message from the user equipment to the at least one network entityof the communication system. The methodology 1900 may further compriseapplying transport protection to the generated control plane message,the transport protection comprising providing one or more IEs includingthe user data content of the designated payload container type in aseparate NAS message container, and applying ciphering to the separateNAS message container utilizing a NAS security context of the userequipment. The one or more IEs provided in the separate NAS messagecontainer may comprise at least one of a payload container type IE, apayload container IE, a PDU session identifier IE, a PDU session statusIE, an uplink status IE, and a release assistance indication IE.

If the user equipment is in a connected mode, the generated controlplane message may comprise an uplink NAS data transport message, step1906 may comprise transmitting the generated control plane message fromthe user equipment to the at least one network entity of thecommunication system. Alternatively where the user equipment is in theconnected mode, the generated control plane message comprises a downlinkNAS data transport message, and step 1906 comprises transmitting thegenerated control plane message from the at least one network entity ofthe communication system to the user equipment.

Step 1904 may comprise generating a payload container type informationelement comprising a payload container information element identifierassociated with the designated payload container type, an indication ofa length of the user data to be transmitted, a PDU session identifier, arelease assistance indication specifying when the at least one networkentity of the communication system should release a NAS signalingconnection (e.g., a RRC connection) for transmission of the user databetween the at least one network entity and the user equipment, and theuser data to be transmitted. The release assistance indication maycomprise one of: an indication that the NAS signaling connection shouldbe released subsequent to uplink transmission of the user data in thegenerated control plane message; and an indication that the NASsignaling connection should be released subsequent to uplinktransmission of the user data in the generated control plane message andsubsequent to a next downlink transmission to the user equipment.

Step 1904 may comprise generating a payload container informationelement of a first format responsive to determining that the size of theuser data to be transmitted is below a threshold for large datatransport and above the threshold for small data transport, andgenerating a payload container information element of a second formatresponsive to determining that the size of the user data to betransmitted is below the threshold for large data transport and belowthe threshold for small data transport. The threshold for large datatransport and the threshold for small data transport may be defined in aNAS MO. The payload container information element of the first formatcomprises a first octet comprising a payload container informationelement identifier associated with the designated payload containertype, second and third octets comprising an indication of a length ofthe user data to be transmitted, a fourth octet comprising a PDU sessionidentifier and a release assistance indication, and a plurality ofadditional octets comprising the user data to be transmitted. Thepayload container information element of the second format comprises afirst octet comprising a payload container information elementidentifier associated with the designated payload container type, asecond octet comprising an indication of a length of the user data to betransmitted, a third octet comprising a PDU session identifier and arelease assistance indication, and one or more additional octetscomprising the user data to be transmitted.

Responsive to determining that the size of the user data is at or abovethe threshold for large data transport, the payload data may betransmitted over a user plane between the user equipment and the atleast one network entity of the communication system.

The communication system comprises a 5G communication system and thedata network comprises a PDN. The at least one network entity of thecommunication system may comprise an AMF of the 5G communication system.The methodology 1900 may be performed by the AMF. If the user data to betransmitted originates at the user equipment, the AMF may initiate adata transfer request to a SMF of the 5G communication system forforwarding to at least one of a UPF and an NEF of the 5G communicationsystem. The data transfer request forwarded to the UPF or the NEF maycomprise a PFCP message.

The particular processing operations and other system functionalitydescribed in conjunction with diagrams of FIGS. 1-19 are presented byway of illustrative example only, and should not be construed aslimiting the scope of the disclosure in any way. Alternative embodimentscan use other types of processing operations and messaging protocols.For example, the ordering of the steps may be varied in otherembodiments, or certain steps may be performed at least in partconcurrently with one another rather than serially. Also, one or more ofthe steps may be repeated periodically, or multiple instances of themethods can be performed in parallel with one another.

It should therefore again be emphasized that the various embodimentsdescribed herein are presented by way of illustrative example only andshould not be construed as limiting the scope of the claims. Forexample, alternative embodiments can utilize different communicationsystem configurations, user equipment configurations, base stationconfigurations, authentication and key agreement protocols, key pairprovisioning and usage processes, messaging protocols and messageformats than those described above in the context of the illustrativeembodiments. These and numerous other alternative embodiments within thescope of the appended claims will be readily apparent to those skilledin the art.

Examples

The following examples relate to further embodiments:

Example 1 relates to an apparatus comprising: at least one processor; atleast one memory including computer program code; the at least onememory and the computer program code being configured to, with the atleast one processor, cause the apparatus at least to: determine a sizeof user data to be transmitted from user equipment to a data network;responsive to determining that the size of the user data to betransmitted is below at least a first size threshold, generate a controlplane message comprising the user data to be transmitted and specifyinga designated payload container type reserved for transport of user dataover a control plane from the user equipment to at least one networkentity of a communication system coupling the user equipment to the datanetwork; and transmit the generated control plane message from the userequipment to the at least one network entity of the communicationsystem.

Example 2 relates to an apparatus of example 1, wherein the apparatus ispart of the user equipment.

Example 3 relates to an apparatus of example 2, wherein the userequipment is part of an Internet of Things (IoT) device.

Example 4 relates to an apparatus of example 2, wherein the userequipment is in an idle mode and the generated control plane messagecomprises a control plane service request message with a control planeservice type set to indicate a user equipment-originating request.

Example 5 relates to an apparatus of example 4, further comprisingapplying transport protection to the generated control plane message,the transport protection comprising providing one or more informationelements including the user data content of the designated payloadcontainer type in a separate Non-Access Stratum (NAS) message container,and applying ciphering to the separate NAS message container utilizing aNAS security context of the user equipment.

Example 6 relates to an apparatus of example 5, wherein the one or moreinformation elements provided in the separate NAS message containercomprise at least one of a payload container type information element, apayload container information element, a Protocol Data Unit (PDU)session identifier information element, a PDU session status informationelement, an uplink status information element, and a release assistanceindication information element.

Example 7 relates to an apparatus of example 2, wherein the userequipment is in a connected mode and the generated control plane messagecomprises an uplink Non-Access Stratum (NAS) data transport message.

Example 8 relates to an apparatus of example 1, wherein generating thecontrol plane message comprises generating a payload container typeinformation element comprising: a payload container information elementidentifier associated with the designated payload container type; anindication of a length of the user data to be transmitted; a ProtocolData Unit (PDU) session identifier; a release assistance indicationspecifying when the at least one network entity of the communicationsystem should release a Non-Access Stratum (NAS) signaling connectionfor transmission of the user data between the at least one networkentity and the user equipment; and the user data to be transmitted.

Example 9 relates to an apparatus of example 8, wherein the releaseassistance indication comprises one of: an indication that the NASsignaling connection should be released subsequent to uplinktransmission of the user data in the generated control plane message;and an indication that the NAS signaling connection should be releasedsubsequent to uplink transmission of the user data in the generatedcontrol plane message and subsequent to a next downlink transmission tothe user equipment.

Example 10 relates to an apparatus of example 1, wherein generating thecontrol plane message comprises: generating a payload containerinformation element of a first format responsive to determining that thesize of the user data to be transmitted is below the first sizethreshold and above a second size threshold; and generating a payloadcontainer information element of a second format responsive todetermining that the size of the user data to be transmitted is belowthe first size threshold and above a second size threshold.

Example 11 relates to an apparatus of example 10, wherein the first sizethreshold and the second size threshold are defined in a Non-AccessStratum (NAS) management object (MO).

Example 12 relates to an apparatus of example 10, wherein the payloadcontainer information element of the first format comprises: a firstoctet comprising a payload container information element identifierassociated with the designated payload container type; second and thirdoctets comprising an indication of a length of the user data to betransmitted; a fourth octet comprising a Protocol Data Unit (PDU)session identifier and a release assistance indication; and a pluralityof additional octets comprising the user data to be transmitted.

Example 13 relates to an apparatus of example 10, wherein the payloadcontainer information element of the second format comprises: a firstoctet comprising a payload container information element identifierassociated with the designated payload container type; a second octetcomprising an indication of a length of the user data to be transmitted;a third octet comprising a Protocol Data Unit (PDU) session identifierand a release assistance indication; and one or more additional octetscomprising the user data to be transmitted.

Example 14 relates to an apparatus of example 1, wherein the at leastone memory and the computer program code are further configured to, withthe at least one processor, cause the apparatus to, responsive todetermining that the size of the user data is at or above the first sizethreshold, transmit the payload data over a user plane between the userequipment and the at least one network entity of the communicationsystem.

Example 15 relates to an apparatus of example 1, wherein thecommunication system comprises a 5G communication system and the datanetwork comprises a Packet Data Network (PDN).

Example 16 relates to an apparatus of example 15, wherein the at leastone network entity of the communication system comprises an Access andMobility Management Function (AMF) of the 5G communication system.

Example 17 relates to a method comprising: determining a size of userdata to be transmitted from user equipment to a data network; responsiveto determining that the size of the user data to be transmitted is belowat least a first size threshold, generating a control plane messagecomprising the user data to be transmitted and specifying a designatedpayload container type reserved for transport of user data over acontrol plane from the user equipment to at least one network entity ofa communication system coupling the user equipment to the data network;and transmitting the generated control plane message from the userequipment to the at least one network entity of the communicationsystem.

Example 18 relates to an article of manufacture comprising anon-transitory computer-readable storage medium having embodied thereinexecutable program code that when executed by a processor operativelycoupled to the computer-readable storage medium cause the processor toperform steps of: determining a size of user data to be transmitted fromuser equipment to a data network; responsive to determining that thesize of the user data to be transmitted is below at least a first sizethreshold, generating a control plane message comprising the user datato be transmitted and specifying a designated payload container typereserved for transport of user data over a control plane from the userequipment to at least one network entity of a communication systemcoupling the user equipment to the data network; and transmitting thegenerated control plane message from the user equipment to the at leastone network entity of the communication system.

Example 19 relates to an apparatus comprising: at least one processor;at least one memory including computer program code; the at least onememory and the computer program code being configured to, with the atleast one processor, cause the apparatus at least to: determine a sizeof user data to be transmitted from a data network to user equipment;responsive to determining that the size of the user data to betransmitted is below at least a first size threshold, generate a controlplane message comprising the user data to be transmitted and specifyinga designated payload container type reserved for transport of user dataover a control plane to the user equipment from at least one networkentity of a communication system coupling the user equipment to the datanetwork; and transmit the generated control plane message to the userequipment from the at least one network entity of the communicationsystem.

Example 20 relates to an apparatus of example 19, wherein the userequipment is in a connected mode and the generated control plane messagecomprises a downlink Non-Access Stratum (NAS) data transport message.

Example 21 relates to an apparatus of example 19, wherein thecommunication system comprises a 5G communication system and the datanetwork comprises a Packet Data Network (PDN).

Example 22 relates to an apparatus of example 21, wherein the at leastone network entity of the communication system comprises an Access andMobility Management Function (AMF) of the 5G communication system.

Example 23 relates to an apparatus of example 22, wherein the apparatusprovides the AMF of the 5G communication system.

Example 24 relates to an apparatus of example 23, wherein the at leastone memory and the computer program code are further configured to, withthe at least one processor, cause the apparatus to initiate a datatransfer request from the AMF to a Session Management Function (SMF) ofthe 5G communication system for forwarding to at least one of a UserPlane Function (UPF) and a Network Exposure Function (NEF) of the 5Gcommunication system.

Example 25 relates to an apparatus of example 24, wherein the datatransfer request forwarded to said at least one of the UPF and the NEFcomprises a Packet Forwarding Control Protocol (PFCP) message.

Example 26 relates to a method comprising: determining a size of userdata to be transmitted from a data network to user equipment; responsiveto determining that the size of the user data to be transmitted is belowat least a first size threshold, generating a control plane messagecomprising the user data to be transmitted and specifying a designatedpayload container type reserved for transport of user data over acontrol plane to the user equipment from at least one network entity ofa communication system coupling the user equipment to the data network;and transmitting the generated control plane message to the userequipment from the at least one network entity of the communicationsystem.

Example 27 relates to an article of manufacture comprising anon-transitory computer-readable storage medium having embodied thereinexecutable program code that when executed by a processor operativelycoupled to the computer-readable storage medium cause the processor toperform steps of: determining a size of user data to be transmitted froma data network to user equipment; responsive to determining that thesize of the user data to be transmitted is below at least a first sizethreshold, generating a control plane message comprising the user datato be transmitted and specifying a designated payload container typereserved for transport of user data over a control plane to the userequipment from at least one network entity of a communication systemcoupling the user equipment to the data network; and transmitting thegenerated control plane message to the user equipment from the at leastone network entity of the communication system.

In some embodiments, certain ones of the operations above may bemodified or further amplified. Furthermore, in some embodiments,additional optional operations may be included. Modifications,additions, or amplifications to the operations above may be performed inany order and in any combination.

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Moreover, although the foregoing descriptions and the associateddrawings describe example embodiments in the context of certain examplecombinations of elements and/or functions, it should be appreciated thatdifferent combinations of elements and/or functions may be provided byalternative embodiments without departing from the scope of the appendedclaims. In this regard, for example, different combinations of elementsand/or functions than those explicitly described above are alsocontemplated as may be set forth in some of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

What is claimed is:
 1. A user equipment comprising: at least oneprocessor; at least one memory including executable program code, the atleast one memory and the executable program code being configured to,with the at least one processor, cause the user equipment at least to:determine a size of user data to be transmitted over a control planefrom the user equipment to at least one network entity of acommunication system; based on a determination that the size of the userdata to be transmitted is below at least a threshold for small datatransport, generate a control plane message comprising the user data tobe transmitted in a small data container over the control plane, whereinthe threshold for small data transport is configured to have a value of254 octets; based on a determination that the size of the user data isabove the threshold for small data transport and below a threshold forlarge data transport, generate a control plane message comprising theuser data to be transmitted and specifying a large data container fortransport of large user data over the control plane; and transmit thegenerated control plane message from the user equipment to the at leastone network entity of the communication system, wherein generating thecontrol plane message comprises: generating a payload containerinformation element of a first format based on a determination that thesize of the user data to be transmitted is below the threshold for largedata transport and above the threshold for small data transport, whereinthe payload container information element of the first format comprisestwo octets comprising an indication of a length of the user data to betransmitted, and generating a payload container information element of asecond format based on a determination that the size of the user data tobe transmitted is below the threshold for large data transport and belowthe threshold for small data transport, wherein the payload containerinformation element of the second format comprises one octet comprisingan indication of a length of the user data to be transmitted.
 2. Theuser equipment of claim 1, wherein the at least one memory and theexecutable program code are further configured to, with the at least oneprocessor, cause the user equipment at least to: transmit the generatedcontrol plane message from the user equipment to the at least onenetwork entity of the communication system for transmission of the userdata via the at least one network entity to a data network.
 3. The userequipment of claim 1, wherein the user equipment is part of an Internetof Things (IoT) device.
 4. The user equipment of claim 1, wherein theuser equipment is in an idle mode and the generated control planemessage comprises a control plane service request message with a controlplane service type set to indicate a user equipment-originating request.5. The user equipment of claim 4, wherein the at least one memory andthe executable program code are further configured to, with the at leastone processor, cause the user equipment at least to: apply transportprotection to one or more non-cleartext information elements of thegenerated control plane message, the transport protection comprisingproviding one or more non-cleartext information elements including theuser data content of the data container in a separate Non-Access Stratum(NAS) message container; and apply ciphering to the value part ofseparate NAS message container utilizing a NAS security context of theuser equipment.
 6. The user equipment of claim 5, wherein the one ormore information elements provided in the separate NAS message containercomprise at least one of a payload container type information element, apayload container information element, a Protocol Data Unit (PDU)session identifier information element, a PDU session status informationelement, an uplink status information element, and a release assistanceindication information element.
 7. The user equipment of claim 1,wherein the user equipment is in a connected mode and the generatedcontrol plane message comprises an uplink Non-Access Stratum (NAS) datatransport message.
 8. The user equipment of claim 1, wherein generatingthe control plane message comprises generating a payload container typeinformation element comprising: a payload container information elementidentifier associated with the small data container; an indication of alength of the user data to be transmitted; a Protocol Data Unit (PDU)session identifier; a release assistance indication specifying when theat least one network entity of the communication system should release aNon-Access Stratum (NAS) signaling connection for transmission of theuser data between the at least one network entity and the userequipment; and the user data to be transmitted.
 9. The user equipment ofclaim 8, wherein the release assistance indication comprises at leastone of: an indication that the NAS signaling connection should bereleased subsequent to uplink transmission of the user data in thegenerated control plane message; or an indication that the NAS signalingconnection should be released subsequent to uplink transmission of theuser data in the generated control plane message and subsequent to anext downlink transmission to the user equipment.
 10. The user equipmentof claim 1, wherein the payload container information element of thefirst format is a CIoT user data container, and wherein the payloadcontainer information element of the second format is a CIoT small datacontainer information element.
 11. The user equipment of claim 1,wherein the threshold for large data transport and the threshold forsmall data transport are defined in a Non-Access Stratum (NAS)management object (MO).
 12. The user equipment of claim 1, wherein thepayload container information element of the first format comprises oneor more of the following: a first octet comprising a payload containerinformation element identifier associated with the large data container;the two octets as second and third octets; a fourth octet comprising aProtocol Data Unit (PDU) session identifier and a release assistanceindication; or a plurality of additional octets comprising the user datato be transmitted.
 13. The user equipment of claim 1, wherein thepayload container information element of the second format comprises: afirst octet comprising a payload container information elementidentifier associated with the small data container; the one octet as asecond octet; a third octet comprising a Protocol Data Unit (PDU)session identifier and a release assistance indication; and one or moreadditional octets comprising the user data to be transmitted.
 14. Theuser equipment of claim 1, wherein the communication system comprises afifth-generation (5G) communication system and the data networkcomprises a Packet Data Network (PDN).
 15. The user equipment of claim14, wherein the at least one network entity of the communication systemcomprises an Access and Mobility Management Function (AMF) of the 5Gcommunication system.
 16. The user equipment of claim 1, wherein the atleast one memory and the executable program code are further configuredto, with the at least one processor, cause the user equipment at leastto: based on a determination that the size of the user data to betransmitted is up to 254 octets, determine that the size of the userdata to be transmitted is below the threshold for small data transport.17. A method comprising: determining a size of user data to betransmitted over a control plane from user equipment to at least onenetwork entity of a communication system; based on a determination thatthe size of the user data to be transmitted is below at least athreshold for small data transport, generating a control plane messagecomprising the user data to be transmitted in a small data containerover the control plane, wherein the threshold for small data transportis configured to have a value of 254 octets; based on a determinationthat the size of the user data is above the threshold for small datatransport and below a threshold for large data transport, generating acontrol plane message comprising the user data to be transmitted andspecifying a large data container for transport of large user data overthe control plane; and transmitting the generated control plane messagefrom the user equipment to the at least one network entity of thecommunication system, wherein generating the control plane messagecomprises: generating a payload container information element of a firstformat based on a determination that the size of the user data to betransmitted is below the threshold for large data transport and abovethe threshold for small data transport, wherein the payload containerinformation element of the first format comprises two octets comprisingan indication of a length of the user data to be transmitted, andgenerating a payload container information element of a second formatbased on a determination that the size of the user data to betransmitted is below the threshold for large data transport and belowthe threshold for small data transport, wherein the payload containerinformation element of the second format comprises one octet comprisingan indication of a length of the user data to be transmitted.
 18. Themethod of claim 17, further comprising: transmitting the generatedcontrol plane message from the user equipment to the at least onenetwork entity of the communication system for transmission of the userdata via the at least one network entity to a data network.
 19. Themethod of claim 17, wherein the user equipment is in an idle mode andthe generated control plane message comprises a control plane servicerequest message with a control plane service type set to indicate a userequipment-originating request, wherein the method further comprises:applying transport protection to one or more non-cleartext informationelements of the generated control plane message, the transportprotection comprising providing one or more non-cleartext informationelements including the user data content of the data container in aseparate Non-Access Stratum (NAS) message container; and applyingciphering to the value part of separate NAS message container utilizinga NAS security context of the user equipment.
 20. A computer programproduct comprising a non-transitory computer-readable storage mediumhaving embodied therein executable program code that when executed by aprocessor operatively coupled to the computer-readable storage mediumcause the processor to perform steps of: determining a size of user datato be transmitted over a control plane from user equipment to at leastone network entity of a communication system; based on a determinationthat the size of the user data to be transmitted is below at least athreshold for small data transport, generating a control plane messagecomprising the user data to be transmitted in a small data containerover the control plane, wherein the threshold for small data transportis configured to have a value of 254 octets; based on a determinationthat the size of the user data is above the threshold for small datatransport and below a threshold for large data transport, generating acontrol plane message comprising the user data to be transmitted andspecifying a large data container for transport of large user data overthe control plane; and transmitting the generated control plane messagefrom the user equipment to the at least one network entity of thecommunication system, wherein generating the control plane messagecomprises: generating a payload container information element of a firstformat based on a determination that the size of the user data to betransmitted is below the threshold for large data transport and abovethe threshold for small data transport, wherein the payload containerinformation element of the first format comprises two octets comprisingan indication of a length of the user data to be transmitted, andgenerating a payload container information element of a second formatbased on a determination that the size of the user data to betransmitted is below the threshold for large data transport and belowthe threshold for small data transport, wherein the payload containerinformation element of the second format comprises one octet comprisingan indication of a length of the user data to be transmitted.